-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show slatepack QR codes #655
Conversation
If I recall correctly this was requested by @marekyggdrasil, I will notice him. |
Really cool! Just one question @cliik , what happens if user runs the command with a tiny window and slatepack is not visible. Then adjustes the terminal window size, will the QR code become properly visible or is it required to run the command again in terminal window of larger dimensions? |
Good idea. I will make it optional.
@marekyggdrasil the QR is just a string of characters. If you resize your terminal (depending on your terminal settings), it should show the QR code correctly. At the end of the day, if you want, you can copy+paste the characters into any other text editor to see the QR code outside of the terminal. Its potentially possible to render the QR code as an image instead, and save the image to a file. Or automatically open the image in a pop-up window, but I think this would be much more complicated, add system dependencies, and not be easy to do cross-platform. Just printing characters in the terminal seemed like the best balance of functionality & simplicity. |
@stakervali 97c10bd makes the QR codes optional, and I agree this improves UX. Thanks for the suggestion. |
I totally agree, that would be an overkill. I think the way you designed it is a perfect compromise between usability and extra overhead. |
This all looks good, thanks for the PR! |
Resolves stakervali/grin-wishlist#12.
This PR addresses the slatepack QR wishlist feature.
This PR shows a QR code when slatepacks are generated. The second slatepack (e.g. response when receiving) results in quite a large QR code, so I think someone should approve that from a UX perspective, but below is an example of the QR output when initiating a send.